User Permissions and Data Security in Tableau

Course: Tableau Training

Topic: User Permissions, Access Control, Authentication, Authorization, and Data Security

Explore the course: Explore Tableau Training at JustAcademy

Book a demo: Register for a Tableau Course Demo

1. Introduction to User Permissions and Data Security

User permissions and data security are essential parts of managing Tableau dashboards, workbooks, projects, published data sources, and reports. They determine who can access information, what actions users can perform, and which records or data values they are allowed to see.

In an organization, different employees need different levels of access. A sales manager may need to view regional sales figures, while a finance manager may need access to revenue and expense reports. An administrator may need to publish workbooks and manage users, while a regular viewer may only need to open dashboards and interact with available filters.

Tableau provides several security mechanisms, including site roles, content permissions, user groups, authentication, data source credentials, and row-level security. These mechanisms work together to protect confidential information while allowing authorized users to perform their work.

Learning Objectives

• Understand user permissions and data security in Tableau.
• Differentiate authentication from authorization.
• Understand Tableau licenses, site roles, groups, and permission capabilities.
• Manage access to projects, workbooks, views, and data sources.
• Understand row-level security and user filters.
• Learn about database credentials and data source authentication.
• Apply the principle of least privilege.
• Configure and test permissions using practical examples.
• Recognize common security risks and learn how to prevent them.

2. What Are User Permissions in Tableau?

User permissions define which actions a user or group is allowed to perform on a particular Tableau content asset. These actions are represented by capabilities such as viewing, publishing, editing, downloading, moving, or deleting content.

Permissions are associated with content, such as projects, workbooks, views, published data sources, and other supported assets. A user may have permission to view one workbook but not another.

Example

Consider a company that publishes three Tableau dashboards:

• Sales Dashboard: Available to the sales team.
• Finance Dashboard: Available to authorized finance employees.
• Executive Dashboard: Available to senior management.

The administrator can configure different access rules for each dashboard. Employees should only receive the permissions required for their responsibilities.

Common Permission Capabilities

Important: The available capabilities depend on the asset type, Tableau version, license, site role, ownership, and project configuration. Granting a capability in a permission rule does not guarantee that the user can perform the action if their site role or another applicable rule prevents it.

Official documentation: Tableau Permissions.

3. What Is Data Security in Tableau?

Data security is the practice of protecting information from unauthorized access, disclosure, modification, or misuse. In Tableau, security includes controlling access to published content, protecting connections to underlying databases, and ensuring users see only the data they are authorized to view.

Examples of Sensitive Data

• Customer names, email addresses, and phone numbers.
• Employee salary and performance information.
• Sales revenue, profit margins, and financial forecasts.
• Customer purchase history and account information.
• Business strategies and confidential operational reports.
• Personally identifiable information and other regulated data.

Why Data Security Matters

• Prevents unauthorized users from accessing confidential information.
• Reduces the risk of accidental data disclosure.
• Supports organizational policies and regulatory obligations.
• Helps protect business information and customer privacy.
• Ensures users receive information appropriate to their responsibilities.
• Improves accountability for access to important reports and data sources.

4. Authentication vs. Authorization

Authentication and authorization are related but different security concepts.

4.1 Authentication

Authentication verifies the identity of a person or system attempting to sign in. It answers the question: Who are you?

Examples include signing in with a username and password, using an organization's identity provider, or using multi-factor authentication where configured and supported.

4.2 Authorization

Authorization determines what an authenticated user is allowed to access or do. It answers the question: What are you allowed to do?

Examples include permission to view a dashboard, publish a workbook, download a data source, or view only the sales records for an assigned region.

Example: An employee successfully signs in to Tableau. Authentication has succeeded. However, the employee still cannot open a confidential finance workbook unless the applicable authorization rules allow access.

5. Understanding Tableau Licenses, Site Roles, and Permissions

Tableau uses licenses, site roles, and permissions to control different aspects of access. These concepts are related, but they are not interchangeable.

5.1 Licenses

A license determines the licensed level of Tableau functionality available to a user. Tableau commonly uses Creator, Explorer, and Viewer license levels, with the exact capabilities depending on the deployment and product configuration.

• Creator: Generally supports creating and publishing content and working with data, subject to the assigned site role and permissions.
• Explorer: Supports interactive exploration and, depending on the specific role and configuration, some publishing or editing workflows.
• Viewer: Primarily supports viewing and interacting with published content within permitted capabilities.

5.2 Site Roles

A site role defines the maximum level of functionality a user can have on a Tableau site and identifies whether the user has an administrator role. Examples include Creator, Explorer, Viewer, and administrator roles.

5.3 Content Permissions

Content permissions determine what a user can do with a specific project, workbook, view, or data source, within the limits of their site role and other applicable rules.

Important: A user can have a Viewer site role and still be unable to access a workbook if its effective permissions do not grant viewing access. Conversely, granting a Viewer a capability that exceeds the role's allowed functionality does not override the site role's limits.

Official documentation: Permissions, Site Roles, and Licenses.

6. Understanding User Groups in Tableau

A group is a collection of users who share a common purpose, department, responsibility, or access requirement. Groups simplify permission management because an administrator can assign rules to a group instead of configuring every user separately.

Examples of Groups

• Sales Team
• Finance Team
• Human Resources
• Regional Managers
• Executive Leadership
• Data Analysts
• Dashboard Viewers

Benefits of Using Groups

• Reduces repetitive administration.
• Makes permission rules easier to understand and maintain.
• Helps maintain consistent access for employees with similar responsibilities.
• Supports onboarding and offboarding workflows.
• Improves auditing and access reviews.

Example

Suppose 40 sales employees need access to the Sales Dashboard. Instead of assigning view access individually, create or use a Sales Team group and grant the group the appropriate permissions.

When a new employee joins the sales department, add them to the group. When an employee leaves the department, remove them from the group and review whether they need any other access removed.

Official documentation: Quick Start: Permissions.

7. Understanding Permission Rules: Allowed, Denied, and Unspecified

Tableau permission rules determine whether a capability is allowed, denied, or unspecified for a user or group on a particular content asset.

7.1 Allowed

Allowed means the rule grants a capability, provided the capability is within the user's site role and no applicable higher-precedence condition prevents it.

7.2 Denied

Denied means the rule explicitly denies the capability. A denial in an applicable rule can prevent a capability from being granted through another group rule.

7.3 Unspecified

Unspecified means the rule does not explicitly grant or deny the capability. If no other applicable condition grants the capability, access is denied.

How Tableau Determines Effective Permissions

Effective permissions are the capabilities a user can actually exercise after Tableau evaluates the relevant rules and conditions.

• The user's site role limits the maximum capabilities available.
• Administrator roles, ownership, and project responsibilities can affect access.
• User-specific rules and group rules are evaluated.
• Applicable denials can prevent capabilities from being granted.
• Permission settings at different content levels can affect the final result.
• Unspecified capabilities are not automatically granted.

Because the result can depend on several rules, administrators should inspect effective permissions instead of assuming that one permission rule tells the whole story.

Official documentation: Tableau Effective Permissions.

8. Managing Permissions for Projects, Workbooks, and Data Sources

Tableau content is organized into projects and assets. Projects help organize content, while workbooks, views, and published data sources contain the dashboards and data resources that users access.

8.1 Project-Level Permissions

Project-level permission rules provide a centralized way to manage access to content in a project. Depending on the project's asset-permissions configuration, these rules can serve as defaults or be locked to keep permissions consistent across content in the project hierarchy.

8.2 Workbook and View Permissions

Workbook and view permissions control what users can do with published visualizations. A user may be allowed to view a dashboard but not edit or download its workbook.

8.3 Data Source Permissions

Data source permissions control which users can connect to or interact with a published data source, according to the available capabilities and configuration. These permissions are separate from permissions to view a workbook that uses the data source.

Recommended Permission Management Approach

1. Organize content into projects based on departments, teams, or data sensitivity.
2. Create user groups that represent business roles.
3. Assign permissions to groups wherever practical.
4. Use project-level permission rules for centralized administration.
5. Lock project permissions when consistent inheritance is required and suitable.
6. Use customizable asset permissions only when specific content needs different access.
7. Review effective permissions for important or sensitive assets.

Example: Department-Based Access

Official documentation: Manage Tableau Permissions.

9. What Is Row-Level Security?

Row-level security (RLS) restricts which rows of a dataset a user can access. Instead of simply granting or denying access to an entire dashboard, RLS allows authorized users to see only the records relevant to them.

Example

A company has sales records for the West, East, North, and South regions. Each regional manager should see only their own region's sales records.

With properly implemented RLS, users do not receive access to other regions' rows merely because they can open the same dashboard.

Common Approaches to Row-Level Security

• User filters: Filter records based on the identity of the current Tableau user.
• Entitlement or mapping tables: Maintain a mapping between users or groups and the records they may access.
• Database-enforced security: Use database security features where the architecture supports the required identity and authorization behavior.
• Virtual connections and data policies: Where the relevant Tableau product and licensing support them, use centrally managed policies to govern data access.

The appropriate method depends on the data architecture, deployment, product version, licensing, identity setup, and whether security must be enforced consistently across multiple access paths.

10. Implementing a User Filter for Row-Level Security

Tableau user filters can restrict the data displayed in a published view based on the identity of the current user. A common example is allowing regional managers to see only their assigned region.

Example Dataset

Region,Sales
West,150000
East,120000
North,90000
South,110000

Suppose each manager should see sales only for their assigned region. A user filter can associate the signed-in user's identity with the appropriate region and filter the records accordingly.

General Implementation Steps

1. Prepare a reliable mapping between Tableau users and the regions or records they are allowed to access.
2. Open the workbook or data source in Tableau Desktop.
3. Identify the field that determines which records each user can see, such as Region.
4. Configure the user filter using the relevant users, groups, or identity-based mapping.
5. Apply the filter to the appropriate worksheets or data source, according to the design.
6. Publish the workbook or data source with the intended security configuration.
7. Test the published content using separate accounts representing different access levels.
8. Verify that unauthorized rows are not exposed through other views or data access methods.

Illustrative User Filter Calculation

In a simple workbook, a calculated field may compare the current user's Tableau username with an authorized-user field in the dataset.

[Authorized Username] = USERNAME()

This expression returns TRUE when the current user's Tableau username matches the value in the row. It is only an illustrative building block: a production RLS design must correctly map each user to all authorized rows, account for group membership where needed, and handle unmatched users securely.

Important: A calculated field or worksheet filter is not automatically a complete security solution. Check that users cannot obtain unauthorized data through other worksheets, downloadable data, published data sources, alternate connections, or other access paths. For stronger centralized enforcement, consider a suitable data-source or database security design.

11. User Filters vs. Database Security

Tableau user filters and database security can both contribute to data protection, but they operate at different layers.

Many organizations use a hybrid approach: Tableau permissions protect published content, while the data platform applies appropriate access restrictions to underlying records.

Official documentation: Tableau Data Security.

12. Protecting Published Data Sources and Database Credentials

A published Tableau workbook may use a live database connection or an extract. Security depends not only on who can open the workbook but also on how the underlying data is accessed and which credentials are used.

12.1 Live Connections

A live connection sends queries to the underlying data source as users interact with a view. The data access behavior depends on the configured connection, authentication mode, database permissions, and caching behavior.

12.2 Extracts

An extract is a stored snapshot of data used by Tableau. Extracts can improve performance in many scenarios, but they introduce additional security considerations because data is stored in extract form and may be refreshed on a schedule.

12.3 Embedded Credentials

Some publishing workflows allow authorized credentials to be embedded or stored for refresh or connection access. This can enable unattended refreshes, but it must be configured according to organizational security requirements.

12.4 Recommended Practices

• Use dedicated, appropriately restricted database accounts for Tableau connections.
• Grant only the database permissions needed by the connection.
• Secure saved or embedded credentials and follow the organization's credential-management policy.
• Review who can connect to, download, or republish data sources.
• Check whether extracts contain confidential data and protect their access accordingly.
• Verify refresh credentials and ownership when a workbook or data source is transferred.
• Use database-level controls where required for sensitive information.
• Test the intended access behavior for live connections and extracts separately.

13. Authentication Methods and Sign-In Security

Tableau deployments can support different authentication methods depending on the product, configuration, and organizational identity platform.

Common Methods

• Tableau authentication: Users sign in using the configured Tableau account credentials.
• Single sign-on (SSO): Users authenticate through an organization's identity provider when configured.
• SAML: A standard that can be used to integrate Tableau sign-in with an identity provider.
• Multi-factor authentication (MFA): Requires additional identity verification where supported and enabled.
• Database authentication: Controls access to an underlying database and is separate from signing in to Tableau.

Security Recommendations

• Use organization-approved authentication methods.
• Enable MFA where appropriate and supported.
• Follow password and identity-provider policies.
• Remove or deactivate access when users no longer need it.
• Review service accounts and stored database credentials regularly.
• Do not assume Tableau sign-in automatically grants access to every external database.

Official documentation: Tableau Authentication.

14. Principle of Least Privilege

The principle of least privilege means that users should receive only the access required to perform their assigned tasks, and no more.

Examples

• A dashboard viewer should not automatically receive publishing or deletion permissions.
• A regional manager should not automatically receive access to all regional records.
• A data analyst should receive editing or publishing permissions only for the projects they support.
• A user who does not need to download a data source should not receive download permissions.
• An employee who changes departments should have their previous access reviewed.

How to Apply Least Privilege

1. Identify the user's responsibilities.
2. Determine the content and data needed for those responsibilities.
3. Choose an appropriate license and site role.
4. Add the user to the relevant groups.
5. Grant the minimum necessary content capabilities.
6. Apply row-level security where users should see different records.
7. Test the user's actual access.
8. Review and remove unnecessary permissions periodically.

15. Practical Example: Securing a Company Sales Dashboard

Scenario

A company has sales data for four regions. Sales representatives should see their assigned region's data, regional managers should see their region's performance, and executives should see company-wide summaries.

Security Requirements

• Sales representatives can view their authorized sales dashboards.
• Regional managers can view records for their assigned regions.
• Executives can view approved company-wide reporting.
• Only authorized analysts can edit or publish workbooks.
• Only designated administrators can manage site-level settings and users.
• Access to downloadable data is limited to users who require it.

Suggested Design

Implementation Workflow

1. Create groups for the business roles.
2. Assign users to the appropriate groups.
3. Organize content into projects based on ownership and sensitivity.
4. Set project permissions for the required content types.
5. Use suitable user filters, entitlement mappings, or database controls to enforce row-level access.
6. Configure connection credentials and extract access according to the security design.
7. Test the dashboard using representative user accounts.
8. Document the permissions model and establish a regular access-review process.

16. Step-by-Step: Configuring Permissions in Tableau

The precise interface can differ between Tableau Server, Tableau Cloud, and product versions, but the general process is similar.

Step 1: Open the Relevant Project or Asset

Sign in with an account authorized to manage permissions. Navigate to the project, workbook, or data source that needs access rules.

Step 2: Open the Permissions Dialog

Open the asset's Actions menu and select Permissions, where the option is available to your role and the content configuration.

Step 3: Select a Group or User

Choose an existing group or user. Prefer group-based rules when multiple users require the same access.

Step 4: Choose a Permission Template

Select an appropriate predefined template if it meets the requirement, or customize individual capabilities where necessary.

Step 5: Set the Required Capabilities

Allow only the actions the user or group needs. Leave unnecessary capabilities ungranted, and use explicit denials where the permission design requires them.

Step 6: Save the Changes

Save the permission configuration and confirm that the changes are applied to the intended project or asset.

Step 7: Inspect Effective Permissions

Use the effective-permissions view to understand the access Tableau determines for a user. Investigate unexpected results caused by site roles, group membership, ownership, or conflicting rules.

Step 8: Test Access

Sign in or test using a suitable non-administrator account. Confirm that the user can perform the required tasks and cannot access content or data outside their authorization.

Official guide: Quick Start: Permissions.

17. Common Security Risks and How to Prevent Them

18. Security Testing Checklist

Use this checklist before publishing a dashboard containing confidential or sensitive data.

• Confirm the intended users and groups.
• Verify the site roles and licenses assigned to users.
• Review project, workbook, view, and data-source permissions.
• Inspect effective permissions for important users.
• Verify row-level restrictions using separate test accounts.
• Check whether data can be downloaded or exported by unauthorized users.
• Review live connection and extract authentication behavior.
• Confirm that sensitive credentials are not exposed in documentation or shared files.
• Test the dashboard through the same access path used by real users.
• Verify that unauthorized users cannot access the underlying data through alternate views or data sources.
• Remove access for users who no longer need it.
• Document the expected access rules and the person responsible for maintaining them.

19. Troubleshooting User Permissions and Data Security

20. Practical Exercises

Exercise 1: Create Department Groups

1. Create or identify Sales, Finance, and Executive groups.
2. Assign test users to the appropriate groups.
3. Create a project for each department's reports.
4. Configure group permissions for each project.
5. Test access using representative accounts.

Exercise 2: Test View and Edit Permissions

1. Publish a sample workbook.
2. Grant a test group view access only.
3. Verify that users can open the workbook.
4. Check that they cannot perform editing or publishing tasks that are not granted and not available through their role.
5. Adjust permissions and retest as needed.

Exercise 3: Implement Regional Data Security

1. Create sample sales records for four regions.
2. Create a mapping between test usernames and their authorized regions.
3. Configure an appropriate user-filter or row-level security method.
4. Publish the workbook using the intended security configuration.
5. Test each region using separate user accounts.
6. Verify that each account sees only the intended records.

Exercise 4: Conduct a Security Audit

1. Choose a sample Tableau project.
2. List the users and groups that have access.
3. Identify unnecessary download, edit, publish, and delete capabilities.
4. Review the effective permissions for a sample of users.
5. Make approved corrections.
6. Document the results and establish a date for the next review.

21. Interview Questions and Answers

Q1. What are user permissions in Tableau?

Answer: User permissions determine which actions a user or group can perform on content such as projects, workbooks, views, and data sources.

Q2. What is data security?

Answer: Data security protects information from unauthorized access, disclosure, modification, and misuse. In Tableau, it includes content access control, data-source security, and restrictions on which records users can view.

Q3. What is the difference between authentication and authorization?

Answer: Authentication verifies a user's identity, while authorization determines what that authenticated user is permitted to access or do.

Q4. What is the difference between a site role and a permission?

Answer: A site role defines the user's maximum capabilities and administrator status on a site. Permissions control specific actions on content assets within those limits.

Q5. Why are groups useful in Tableau?

Answer: Groups allow administrators to manage permissions for multiple users together, improving consistency and reducing administrative work.

Q6. What are Allowed, Denied, and Unspecified permissions?

Answer: Allowed grants a capability subject to other conditions; Denied explicitly blocks it; Unspecified does not grant it by itself.

Q7. What are effective permissions?

Answer: Effective permissions are the capabilities a user can actually exercise after Tableau evaluates site roles, ownership, group membership, and applicable permission rules.

Q8. What is row-level security?

Answer: Row-level security restricts which records a user can access. For example, a regional manager can be limited to sales records for their assigned region.

Q9. How can Tableau implement row-level security?

Answer: Depending on the architecture, it can use user filters, entitlement mappings, supported centralized data policies, database-level controls, or a combination of these approaches.

Q10. What is the principle of least privilege?

Answer: It means granting users only the access and capabilities needed for their work, avoiding unnecessary permissions.

Q11. How can an administrator reduce unauthorized access?

Answer: Use appropriate roles and group-based permissions, restrict downloads where necessary, implement row-level security, protect credentials, and regularly review access.

Q12. What is the difference between a live connection and an extract from a security perspective?

Answer: A live connection queries the underlying source according to its connection and authentication configuration. An extract stores a snapshot of data, so its contents, access permissions, refresh process, and download exposure must also be protected.

Q13. Why should effective permissions be checked?

Answer: A user's actual access may differ from what one rule appears to grant because of site-role limits, group membership, ownership, and conflicting rules.

Q14. How should an organization revoke access when an employee leaves?

Answer: Remove or deactivate the user's Tableau access according to policy, review group memberships and ownership, and revoke associated credentials or tokens where appropriate.

Q15. How do you test row-level security?

Answer: Test using separate accounts representing different access levels, compare the records each account can see, and verify that other views, data sources, and download paths do not expose unauthorized records.

22. Quick Revision Notes

• Authentication verifies identity.
• Authorization controls access and actions.
• Licenses and site roles apply to users; permission capabilities apply to content.
• Groups simplify access management.
• Project-level permissions support centralized administration.
• Effective permissions reflect the final result of applicable access rules.
• Unspecified capabilities are not automatically granted.
• Row-level security restricts the records a user can access.
• User filters and database security operate at different layers.
• Live connections and extracts have different data-access and storage considerations.
• Protect credentials and restrict unnecessary download access.
• Follow the principle of least privilege.
• Test security using representative user accounts before release.
• Review access regularly and revoke permissions when they are no longer needed.

23. Official Tableau Learning Resources

• Tableau Permissions
• Effective Permissions
• Permissions, Site Roles, and Licenses
• Tableau Data Security
• Tableau Authentication
• Tableau Cloud Security
• Quick Start: Permissions

24. Tableau Training and Course Demo

Build your Tableau skills by learning dashboard creation, data visualization, access control, and secure data management through structured lessons and practical exercises.

Explore Tableau Training at JustAcademy

Register for a Tableau Course Demo

25. Conclusion

User permissions and data security are essential for protecting Tableau content and ensuring that information reaches the right people. Effective security requires more than hiding a dashboard: it involves suitable licenses and site roles, clear permission rules, group-based administration, secure data connections, and row-level restrictions when users should see different records.

Use the principle of least privilege, inspect effective permissions, protect credentials and extracts, and test access through realistic user accounts. Regular reviews help ensure that permissions remain appropriate as employees, projects, and business requirements change.

Key takeaway: Give users the minimum access they need, secure the underlying data as well as the dashboards, and verify the complete access path before publishing confidential information.

Continue learning: Explore Tableau Training | Register for a Tableau Course Demo